add CI for pull requests, deploy docs when main is updated#7
Merged
bryangingechen merged 2 commits intomainfrom Feb 16, 2025
Merged
add CI for pull requests, deploy docs when main is updated#7bryangingechen merged 2 commits intomainfrom
bryangingechen merged 2 commits intomainfrom
Conversation
Note that this uses the `pull_request` event so it runs the code in the PR branch and does not have access to repo secrets (I don't think there are any relevant ones here though). We need to be extra careful here with external PRs because we run on self-hosted runners.
Contributor
Author
|
This will probably fail CI until the current breakage in |
deploy docs when main is updated
bryangingechen
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note that this uses the
pull_requestevent so it runs the code in the PR branch and does not have access to repo secrets (I don't think there are any relevant ones here though). We need to be extra careful here with external PRs because we run on self-hosted runners.